When you are designing a HyperCard stack, simplicity should be the watchword. Whether you are expecting users to browse through your stack using HyperDA or not, keeping your designs as simple as possible will have numerous other rewards. Ease of maintenance, frequently faster execution, and greater productivity for you as a designer-programmer are among the most significant advantages of simple design.
You will encounter some design problems in constructing stacks to be compatible with HyperDA. Many of them will not lend themselves to a good solution or work-around; if these problem-causing routines are essential to your stack, then you will simply not be able to offer your users the convenience and power of HyperDA.
However, there are many instances where a little creative thought can yield work-arounds and programming solutions to what appear at first blush to be all but insurmountable obstacles to HyperDA compatibility. Let’s look at three examples of such work-arounds. Future editions of this stack will include more suggestions. We are always on the lookout for new ideas in this arena, so if you run into a seeming obstacle and find a good way around it, write us and let us know. We’ll give you credit!
